RANGER-5301: Fix InvalidDefaultArgInFrom Warnings in docker build #813
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
Warnings from BuildKit during the docker build:
To silence these warnings, the best way seems to be to use sentinel placeholders instead of duplicating raw values from
.envfile. Maintaining versions in multiple files is an overhead so using placeholders is a good approach to take.Update
Using placeholders doesn't solve the warnings, so using default values - the values may remain the same over time as overrides are in place using
docker composeHow was this patch tested?
The warnings are no longer seen in the docker builds in CI.